Skip to content

Add optional package name arguments to wp package update #208

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
swissspidy merged 5 commits into from
Jan 20, 2026
Merged

Add optional package name arguments to wp package update #208

swissspidy merged 5 commits into from
Jan 20, 2026

Conversation

Copy link
Contributor

Copilot AI commented Jan 12, 2026 •
edited
Loading

  • Understand the current implementation of wp package update command
  • Review Composer's setUpdateAllowList() method to update specific packages
  • Modify the update() method signature to accept optional package name arguments
  • Add logic to handle specific package updates using setUpdateAllowList()
  • Update command documentation/PHPDoc
  • Add Behat tests for updating specific packages
  • Address code review feedback
    • Updated method description to reflect it can update specific packages
    • Improved success message logic by extracting count check
  • Address PR review feedback
    • Track actual package updates using Composer event listener
    • Provide accurate messaging when some packages don't have updates available
    • Handle cases where packages are already at latest version
  • Run lint, phpcs, and phpstan checks (all pass)
  • Run PHPUnit tests (all pass)
  • Run CodeQL security check (no issues)
  • Final verification complete

Summary

Successfully implemented optional package name arguments for wp package update command with full backward compatibility and accurate update tracking. The implementation now:

✅ Tracks actual package updates via Composer events
✅ Provides accurate success messages based on what was actually updated
✅ Handles scenarios where packages are already up to date
✅ Distinguishes between partial and full update success

Original prompt

This section details on the original issue you should resolve

<issue_title>Add package name argument to wp package update</issue_title>
<issue_description>The wp package update command updates all outdated packages. I'd like to be able to update one specific package like so:

wp package update vendor/package-name

I'm also tempted to suggest bringing it in line with the plugin update and theme update commands, which at minimum would...

  • require one or more package name arguments (which, I acknowledge, breaks existing functionality, and is very bad)
  • suggest the addition of an --all flag to re-implement the current behavior (wp package update --all)

Thoughts?</issue_description>

<agent_instructions>Add an optional positional argument for the wp package update command.</agent_instructions>

Comments on the Issue (you are @copilot in this section)

@swissspidy Let's start with supporting one or more packages to be updated, maintaining backward compatibility.

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

@github-actions github-actions bot added command:package-update Related to 'package update' command scope:distribution Related to distribution state:unconfirmed labels Jan 12, 2026
@codecov

This comment was marked as resolved.

Sign in to view
Copilot AI and others added 2 commits January 12, 2026 12:34
@swissspidy
Add optional package name argument to wp package update command
c5bd2b3 
Co-authored-by: swissspidy <841956+swissspidy@users.noreply.github.com>
@swissspidy
Address code review feedback - improve method description and message…
0f8cfc6 
… logic

Co-authored-by: swissspidy <841956+swissspidy@users.noreply.github.com>
Copilot AI changed the title [WIP] Add package name argument to wp package update Add optional package name arguments to wp package update Jan 12, 2026
Copilot AI requested a review from swissspidy January 12, 2026 12:38
@swissspidy swissspidy requested a review from Copilot January 12, 2026 13:40

This comment was marked as resolved.

Sign in to view

@swissspidy
Track actual package updates and provide accurate success messaging
fb1acec 
- Add event listener for 'post-package-update' to track which packages are actually updated
- Differentiate success messages based on update outcomes:
  - "Package already at latest version" for single package with no update
  - "Packages already at latest versions" for multiple packages with no updates
  - "Package updated successfully" for single package updated
  - "All N packages updated successfully" when all requested packages are updated
  - "Updated X of Y packages" when only some packages are updated
- Update tests to reflect new messaging behavior
- Add test scenario for package already at latest version

Co-authored-by: swissspidy <841956+swissspidy@users.noreply.github.com>
@swissspidy swissspidy marked this pull request as ready for review January 12, 2026 16:34
@swissspidy swissspidy requested a review from a team as a code owner January 12, 2026 16:34
@swissspidy swissspidy mentioned this pull request Jan 12, 2026
Closed
@swissspidy swissspidy merged commit b2b5700 into main Jan 20, 2026
52 of 53 checks passed
@swissspidy swissspidy deleted the copilot/add-package-name-argument branch January 20, 2026 21:42
@swissspidy swissspidy added this to the 2.6.2 milestone Jan 20, 2026
@baizmandesign
Copy link
Contributor

baizmandesign commented Jan 20, 2026

@swissspidy Thanks for taking care of this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

Copilot code review Copilot Copilot left review comments

@swissspidy swissspidy Awaiting requested review from swissspidy

Assignees

@swissspidy swissspidy

Copilot code review Copilot

Labels

command:package-update Related to 'package update' command scope:distribution Related to distribution

Projects

None yet

Milestone

2.6.2

Development

Successfully merging this pull request may close these issues.

Add package name argument to wp package update

3 participants

@baizmandesign @swissspidy